Skip to content

Update contracts.md#79

Merged
tromp merged 1 commit into
mimblewimble:masterfrom
mmaker:patch-3
May 26, 2025
Merged

Update contracts.md#79
tromp merged 1 commit into
mimblewimble:masterfrom
mmaker:patch-3

Conversation

@mmaker
Copy link
Copy Markdown
Contributor

@mmaker mmaker commented Jan 2, 2023

Remove mention of Aggregate Signatures. Formally, an aggregate signature scheme would require an aggregated signature on messages (m_1, .... m_n) to be of the same size as a signature on a single message. We used some slack in [FOS19] to bring Schnorr and BLS under the same framework but Schnorr/MuSig are definitely not know for its aggregation capabilities. MuSig is a multisignature, which is very different -- also they could be seen as part of the big umbrella term of "Schnorr Signatures"

Remove mention of Aggregate Signatures. Formally, an aggregate signature scheme would require an aggregated signature on messages \(m_1, .... m_n\) to be of the same size as a signature on a single message. We used some slack in [FOS19] to bring Schnorr and BLS under the same framework but Schnorr/MuSig are definitely not know for its aggregation capabilities. MuSig is a multisignature, which is very different -- also they could be seen as part of the big umbrella term of "Schnorr Signatures"
@Anynomouss
Copy link
Copy Markdown
Collaborator

@tromp @yeastplume Any thoughts on the above feedback? To my understanding grin does aggregate signatures since the "aggregated signature" of n signatures is of the same length of a single signature, but this is going into the realm of cryptographic definitions which is not my cup of tea.

@tromp tromp merged commit 169abf5 into mimblewimble:master May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants